Honestly, I wonder if we should just remove the relaxed dependencies file. I never end up using it. If I need to test a requirement change locally, I just edit the main constraints file and re-run pip-compile.

Honestly, I wonder if we should just remove the relaxed dependencies file. I never end up using it. If I need to test a requirement change locally, I just edit the main constraints file and re-run pip-compile.

Removing does mean one less thing to deal with. I'm fine with it personally but would like to hear what @felixfontein has to say. The whole point is to give him (and you) a set of dependencies to hack around with for dev purposes, as I'm sure you know.

Wasn't the purpose of the relaxed dependencies to use them for some docsite build (ansible-core devel or ansible devel), so that we'd have an "early warning" in case something breaks?

(I don't use the relaxed deps either.)

Wasn't the purpose of the relaxed dependencies to use them for some docsite build (ansible-core devel or ansible devel), so that we'd have an "early warning" in case something breaks?

(I don't use the relaxed deps either.)

Thanks @felixfontein

From what I recall the relaxed dependencies were intended as a replacement for that one docs/docsite/requirements.txt file so folks could plug in different dependencies and play around with builds without tampering with the "tested" requirements. There aren't any jobs - in jenkins or elsewhere - building with the relaxed requirements either. So if nobody is using them it probably would make sense to drop them altogether.

Should we close this PR?